A number of xbl files don't pass now that bug 1229858 is landed.

Bug 1231828: Fix XBL preprocesser to properly handle fields, entities and handlers. r?miker Fixing some XBL files turned up some bugs in the preprocessor: * XBL fields aren't just simple JS assignements, they are entire JS blocks which are evaluated and the result used for the field. So we don't need eslint to parse them as an assignment. * XBL text can contain entities, in general just replacing every entity with a valid JS token should retain the meaning well enough for eslint's purposes. * Events can have names that aren't valid JS identifiers so just don't use them.

Bug 1231828: Fix JS parsing errors in toolkit and browser XBL files. r?felipe

Comment on attachment 8697634 [details] MozReview Request: Bug 1231828: Fix JS parsing errors in toolkit and browser XBL files. r=felipe https://reviewboard.mozilla.org/r/27681/#review24907

Comment on attachment 8697633 [details] MozReview Request: Bug 1231828: Fix XBL preprocesser to properly handle fields, entities and handlers. r=miker https://reviewboard.mozilla.org/r/27679/#review25067 r+

Comment on attachment 8697633 [details] MozReview Request: Bug 1231828: Fix XBL preprocesser to properly handle fields, entities and handlers. r=miker Review request updated; see interdiff: https://reviewboard.mozilla.org/r/27679/diff/1-2/

Comment on attachment 8697634 [details] MozReview Request: Bug 1231828: Fix JS parsing errors in toolkit and browser XBL files. r=felipe Review request updated; see interdiff: https://reviewboard.mozilla.org/r/27681/diff/1-2/

https://hg.mozilla.org/integration/mozilla-inbound/rev/1df6ac95af8f https://hg.mozilla.org/integration/mozilla-inbound/rev/d897127c0000

https://hg.mozilla.org/mozilla-central/rev/1df6ac95af8f https://hg.mozilla.org/mozilla-central/rev/d897127c0000

Backout: https://hg.mozilla.org/integration/fx-team/rev/5621bf5d87e4

This fix appears to have caused a regression when sorting XUL trees in a Remote XUL deployment (based on the output of mozregression). I've filed bug #1279911 with more details and a test case.